Systems and Methods for Detecting a Travelling Object Vortex

ABSTRACT

Systems and methods of detecting a vortex made by a travelling object is disclosed. Techniques include positioning a media collector to capture a visual media file of the vortex. In some configurations, a graphic recognition algorithm and vortex similarity engine are used to determine whether a visual media file captured by a media collector contains a vortex. In some configurations, a computer may trigger an alert if a travelling object vortex is not expected to be in the visual media file.

CROSS-REFERENCES

This application is a continuation of U.S. patent application Ser. No. 17/987,560 filed Nov. 15, 2022, which claims the benefit of priority to U.S. Provisional Application 63/352,731 filed Jun. 16, 2022.

STATEMENT OF GOVERNMENT INTEREST

The present invention was made by employees of the United States Department of Homeland Security in the performance of their official duties.

FIELD

The discussion below relates generally to systems and method for detecting a vortex generated by a travelling object.

BACKGROUND

U.S. Pat. No. 10,349,985 discloses a turbulence-free camera system and image enhancement technology, the contents of which are incorporated by reference in its entirety. This patent describes a camera system for application in long distance imaging such as satellite and aircraft to ground based imaging.

U.S. Pat. No. 8,339,583 discloses a system for detecting clear air turbulence, the contents of which are incorporated by reference in its entirety. The system compares a set of images to detect a change in refection of light due to turbulence. The system produces an indication of the area of turbulence in the scene.

U.S. Pat. No. 6,736,148 explains techniques and algorithms for image processing, the contents of which are incorporated by reference in its entirety.

U.S. Pat. No. 5,537,641 provides a method for physically-based modeling of three dimensional (3D) general fluid animation in computer graphics. For example, two dimensional (2D) Navier-Stokes equations are solved using a Computational Fluid Dynamics method. U.S. Pat. No. 5,537,641 is incorporated by reference in its entirety.

U.S. Pat. No. 8,682,626 provides a method and system for comprehensive patient-specific modeling of the heart, the contents of which are incorporated by reference in its entirety. This patent discloses using a patient-specific anatomy as input to a 3D Navier-Stokes solver that derives realistic hemodynamics.

SUMMARY

Despite these improvements their remains an unmet need for a technology that detect a vortex generated by a travelling object. Aspects of the presently disclosed technology provide various systems of method for detecting a vortex made by a travelling object. Some configurations include systems and methods for detecting UAS (unmanned aircraft systems) and/or UAV (unmanned aerial vehicles.)

For example, a method of detecting a travelling object travelling through the air is disclosed. The method may comprise positioning a media collector to capture a visual media file of a region of the air containing air molecules. The media collector may capture a visual media file of a vortex generated by the travelling object. A computer may receive the visual media file from the media collector. The computer may detect whether the visual media file has elements in common with a vortex generated by a travelling object.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A depicts a schematic diagram of a visual media classifier and flight plan logic.

FIG. 1B depicts a cross-sectional view of vortex generated by an airborne object.

FIG. 1C depicts some schematic views of unmanned aircraft

FIG. 2 depicts a flow chart of a method of detecting whether a visual media file has elements in common with a vortex generated by a travelling object.

FIG. 2 depicts a flowchart of a method of detecting whether a visual media file has elements in common with a vortex generated by a travelling object.

FIG. 3 depicts a schematic diagram of a vortex similarity engine.

FIG. 4 depicts a flowchart of processes of the vortex similarity engine.

FIG. 5 is a schematic diagram of a graphic recognition algorithm and graphic property manager.

FIG. 6 also depicts a schematic diagram of the graphic recognition algorithm and graphic property manager. The figure depicts processing multiple visual media files and classifying an unknown visual media file

FIG. 7 depicts a flowchart of a process of determining whether a travelling object is expected to be flying in the field of view of a media collector.

FIG. 8 is a schematic diagram of a flight checker and flight visualizer.

FIG. 9 depicts a flowchart of a process of determining a similarity ratio to indicate whether a visual media file contains a travelling object vortex using a vortex similarity engine.

FIG. 10 is a schematic diagram of the vortex similarity engine using an element similarity profile to generate a travelling object vortex similarity ratio.

FIG. 11 depicts a flowchart of a process of determining an overall travelling object vortex probability based on an aggregation of N similarity ratios using a probability calculator.

FIG. 12 depicts a flowchart of a process of determining an overall travelling object vortex probability based on an aggregation of the three vortex similarity ratios based on visual media files taken at different times.

FIG. 13 depicts a flowchart of a process of determining an overall travelling object vortex probability based on an aggregation of the three vortex similarity ratios based on visual media files taken with different media collectors.

FIG. 14 depicts a schematic diagram of a visual media timing device and visual media classifier.

FIG. 15 depicts a flowchart of whether a computer process for detecting whether video or images resemble a vortex of a travelling object.

FIG. 16 depicts a schematic diagram of a computer process for detecting whether video or images resemble a vortex of a travelling object and whether that travelling object is a registered flight plan.

DETAILED DESCRIPTION OF THE DRAWINGS

FIG. 1A depicts a schematic diagram for a system 100 for detecting a vortex 105 made by a travelling object 110. The system may comprise a media collector 115 configured to capture a region of the air containing air molecules. The media collector may be configured to capture a visual media file 120 of a vortex generated by the travelling object. The system may include a computer 125 configured to receive a visual media file from the media collector.

The travelling object may be a fixed wing airplane, helicopter, missile, projectiles, glider, etc. When the travelling object is travelling through the air, it may be called an airborne object. Some configurations of the invention can detect vortices made by nonairborne travelling objects, e.g. objects travelling on the ground, in the sea, underwater, underground, etc. Discrete examples of nonairborne travelling objects may include vehicles, cars, ships, drills, submarines, etc.

A vortex may be a change in density of the air or a compression of air molecules in the air. A vortex may be generated by an airborne object flying through the air. A vortex may be generated by wings, propeller, fuselage, and other surface pushing a medium (like air or water) out of the way—generating a temporary change in density of that medium. A vortex may be created in other mediums as well such as water. Travelling objects like a boat or submarine may create a vortex. In some configurations, the propeller of the aircraft or travelling object generates a vortex. The vortex may trail the travelling object. The length of a vortex may be much longer than the length of the travelling object. Radar-based technologies might be useful for detecting the travelling object in some cases, but ineffective at detecting a vortex.

FIG. 1B shows a cross-section view of what a vortex might look like as generated by a propeller-based aircraft.

FIG. 1C illustrates some examples UAV (unmanned aerial vehicles). In practice most UAVs are part of a larger UAS (unmanned aircraft system), wherein UAS may also include GPS, ground control, transmissions systems, media collectors, software, etc. Often UAS is controlled by a person or a team on the ground or in another vehicle. The travelling object can be any flying or propelled device (e.g. a missile, shuttle, glider, etc.). FIG. 1C illustrates some specific examples of travelling objects including the Predator A 110A, Harfang 110B, and Global Hawk 110C.

The media collector may be a camera, webcam, smartphone, point and shoot camera, satellite camera, lidar system, video camera, or other electronic device configured to capture and save light with an optic sensor. The media collector may capture visual media files such as pictures, graphics, optic sensor data, videos, video frames, etc. The computer may be a server, laptop, desktop, smartphone, wearable, or other type of computing device. The computer may include a processor, system memory, tangible computer readable storage media, communications circuitry or logic, graphics processor, and a display. The tangible computer readable storage media may store, in a non-transitory manner, instructions for programming or causing the processor of the computer to perform a sequence of steps or instructions. In some configurations, the media collector may include the computer itself, or the media collector and the computer may be separate device. For example, a drone may comprise a media collector with an onboard computer. The computer may be a part of the media collector's circuitry. Or the computer might be a server on the ground, e.g. in an office building. The drone's media collector might stay in communication with the computer with communication circuitry or logic. There may be a delay between when the media collector captures the optic sensor information and when the computer receives the optic sensor information (e.g. the visual media file).

The system may include a visual media classifier 130 configured to determine whether the received visual media file has elements in common with previously captured visual media files featuring a vortex generated by a travelling object.

The system may comprise a light source 135 configured to shine light in the region of the air. The light source may comprise a high number of lumens (e.g. a photo bomb.) The presence of the additional light photons may aid the media collector, computer, and/or graphic recognition algorithm in seeing or detecting the presence of the vortex. The visual media classifier 130 may be configured to generate a similarity value 140 based on how many elements the visual media file has with previously captured and identified travelling object vortices. The visual media classifier 130 may be configured to generate a similarity value 140 based on how similar the elements in the visual media file are to previously captured and identified travelling object vortices.

The system may comprise flight plan logic 145. The flight plan logic may be configured to receive a flight plan 150 from a flight computer 155. A flight plan 150 may be stored using a data structure such as a table or list of information. The flight plan may comprise a plurality of rows and columns of data. The flight plan may comprise a header row. The flight plan may also comprise only a single row or column of data.

The flight plan logic 145 may be configured to determine whether the travelling object is on a registered flight plan. A flight plan may include a flight number, a flight departure area, flight path, flight time, and other information relating to the travelling object and route the plan is scheduled to take or has already completed. For example, the flight plan may include a global position system (GPS) data points or IMU (inertial measurement unit). The computer may be configured to trigger an alarm if: the vortex comparison engine determines the visual media file contains a vortex; and the travelling object is not on a registered flight plan.

Table 1 depicts an exemplary flight plan. In this example, there are five columns of data: a Flight ID (an identifier of a travelling object), a Flight Time (departure time), a Date (departure date), Flight Path (a course and speed for the flight), and a validated flight (a yes/no field that a flight checker, in some embodiments, can save data into to record whether the flight is authorized or approved.)

TABLE 1 Flight Flight Validated ID Time Date Flight Path Flight 0101  6 AM Mar. 19, 1980 Flight Path 1 Approved 0102 10 AM Mar. 21, 1980 Flight Path 2 Unapproved 0103  2 PM Mar. 25, 1980 Flight Path 3 Approved

FIG. 2 depicts a flowchart illustrating a method 200 for detecting a travelling object 240 flying through a region of air 215. The travelling object may create a vortex in the region of air 220. The vortex potentially formed by a change in density or compression of air molecules 225. The method 200 may include positioning a media collector 210 to capture a region of the air containing air molecules, capturing a visual media file 230 of the region of the air, and receiving 160 the visual media file with a computer 235. The computer may be programmed to detect 240 whether the visual media file has elements in common with a vortex generated by a travelling object.

The method may comprise shining a light source 205 in the region of the air. The light source may be a flashlight, a search light, a laser, or other device capable of emitting a beam of photos in an area. The light source may be naturally occurring such as a reflection. The light source may be the sun or the moon.

The method may comprise generating a similarity value 245 based on how many elements the visual media file has with previously captured and identified visual media files of travelling object vortices. Additionally, the method may comprise generating a similarity value based on how similar the elements in the visual media file are to previously captured and identified visual media files of travelling object vortices.

The method may comprise determining whether the travelling object is on a registered flight plan 250. The method may include logging the flight if the travelling object is on a registered flight plan 255. The method may include triggering an alarm if the visual media file is identified to be a vortex and the travelling object is not on the registered flight plan 260.

FIG. 3 depicts a method 300 of generating a similarity profile 325 using a vortex similarity engine 305. As shown, the embodiment of FIG. 3 depicts a method of providing a database of visual media files 310. The database may be contained in a computer or a server. It may also be connected to other processing devices. In the example of FIG. 3 , the vortex similarity engine comprises the database. The vortex similarity engine itself may be embodied as a code executable code non-transitorily stored on computer readable media. A processor may execute that code to generate an instance of the vortex similarity engine (e.g. run or execute the engine.) The engine may also be embodied as circuitry, logic, or other hardware components.

The method shown in FIG. 3 also depicts detecting graphic properties of an image from the database of visual media files with a graphic recognition algorithm 315. The method may include designating the visual media file as a travelling object vortex visual media file if the visual media file depicts a travelling object vortex 320. The method 300 may also include designating the visual media file as not travelling object vortex visual media file if the visual media file does not contain a travelling object vortex. The method may involve identifying a graphic property that some of the travelling object vortex visual media file share; and generating an element similarity profile based on one or more graphic elements identified by the graphic recognition algorithm.

In some embodiments, a graphic property relates to a feature, element or characteristic of the visual media file that can be recognized, generated, and/or captured by a graphics recognition algorithm. The graphics recognition algorithm may be run by a general processor (like a CPU) or by a specialty graphics processor. Information captured by an optic capturing device (e.g. a media collector) may have many graphic properties. The graphic recognition algorithm may be configured to detect these image properties.

Designation of a visual media file as containing a vortex may be accomplished many ways. Designation may be performed by artificial intelligence (e.g. a vortex designator) or by humans. Visual media files may contain metadata that lists whether the image is of a travelling object or a vortex or such information may be contained in a file name.

In FIG. 3 , the step of generating an element similarity profile can be accomplished with 4 steps. In some configurations, only 1, 2, or 3 of these may be used. Additionally, some configurations will repeat these 1-4 steps a plurality of times or include additional steps. The four depicted steps are: identify a graphic property that some of the travelling object vortex visual media files share 330; identify a graphic property that some of the not travelling object vortex visual media files share 335; identify a graphic property that some of the visual media files do not share 340; and identify a graphic property that some of the not travelling object visual media files do not share 345.

TABLE 2 Graphic Properties Graphic Properties in Common Not in Common Vortex Media File Not Vortex Media File

Table 2 shows an example of a data structure that can hold comparison information of graphic properties that may be common or not common to a vortex media file. As shown in Table 2, the vortex engine can use the graphic profile generator to build a data structure that can be used to analyze whether a visual media file containing an unknown subject more closely resembles other visual media file known to depict a vortex or whether the unknown visual media more closely resembles other media files known not to depict a vortex. Similarly, the element similarity profile can be used to determine whether the unknown visual media file has graphic properties that are not similar to properties in a visual media known to depict a vortex. Further, the element similarity profile can be used to determine whether the unknown visual media file has graphic properties that are not similar to properties in a visual media known to not depict a vortex.

An element similarity profile may be a data structure (like an array or a list) that associates properties (e.g. graphic properties) of the visual media file. The data structure may contain organizational data that identifies, for example, probabilities that a certain graphic element will appear in a visual media files depicting a vortex. The data structure may contain organizational data that identifies, for example, probabilities that a certain graphic element will not appear in a visual media files depicting a vortex. The data structure may contain organizational data that identifies, for example, certain graphic elements that are not relevant to whether a visual media file depicts a vortex.

FIG. 4 shows a schematic view of a vortex similarity engine 400. The schematic shows a database of visual media files 405, a graphic recognition algorithm 410, a visual media file designation tool 415, a graphic property identifier 420, an element similarity profile generator 425, and an element similarity profile 430. The graphics recognition algorithm may be configured to generate graphic elements based on characteristics of the images from the database. The visual media file designation tool may be configured to designate the visual media files as a travelling object vortex image if the image depicts a travelling object vortex. The visual media file designation tool 415 may be configured to designate the image as not travelling object vortex image if the image does not depict a travelling object vortex. The graphic property identifier 420 may be configured to identify a graphic property that some of the travelling object vortex images share. The element similarity profile generator 425 may be configured to generate an element similarity profile 430 based on one or more graphic elements identified by the graphic property identifier 420.

FIGS. 5 and 6 depict a method and system 500 for determining whether an unclassified visual media file 670 depicts a vortex. Some configurations comprise providing a visual media file database 505 comprising a first visual media file 510A and second visual media file 510B. In some configurations, the database 505 will comprises many visual media files. FIG. 6 shows media files 615A-615E for example stores in a database 605. Each of the visual media files may have graphic properties 525. The visual media file 510 may contain metadata 530 which indicates whether the visual media file depicts a vortex or not. The metadata may comprise a visual media file designation 520 to designate whether the visual media file depicts a vortex. In some configurations, the database 505 will contain a data structure 535 for storing a label documenting the identification of the visual media file as depicting a vortex or not depicting vortex. The method may include determining a first graphic property 625A of the first visual media file 615A with a graphic recognition algorithm 645; and determining a second graphic property 625B of the second visual media file 615B with the graphic recognition algorithm 645. The method may contain saving the first graphic property and second graphic property with a graphic property manager 550. FIG. 5 shows the graphic property manager 550 saving the graphics property as saved graphic property information 555. Some configurations include requesting or getting the first and second graphic property of the visual media file with a graphic property manager 550. The graphics property manager 550 may submit queries to the database 505 to obtain the graphic property information or it may read the graphic property information from the metadata for example.

In FIG. 6 , an element similarity profile generator 660 may take the graphic property information 555 saved by the graphic property manager 650 to construct an element similarity profile 635. The method may include providing a visual media classifier 665 configured to process an unclassified visual media file 670. A second instance of a graphic recognition algorithm 675 (or it could be the same graphics recognition algorithm in some embodiments) may be used to analyze the unclassified media file 670 to determine one or more graphic properties of the unclassified visual media file. The visual media classifier 665 may create a classified visual media file 680 by classifying the visual media file as depicting or depicting a vortex by processing the graphic properties from the second graphic recognition algorithm and element similarity profile.

The system of FIGS. 5-6 depicts a visual media file database comprising a first visual media file 510A and second visual media file 51B. The database may comprise many visual media files. The system may include a first graphics recognition algorithm 645 configured to determine: a first graphic property 625A of the first visual media file 615A; a second graphic property 625B of the second visual media file 615B; and a third graphic property 625C of the unclassified visual media file 615C. In other configurations, multiple graphic recognition algorithms or instances of the graphic recognition algorithm may be used. The system may comprise a graphic property manager 650 configured to save the first graphic property and second graphic property. In some configurations, the graphic recognition algorithm 645 can perform saving operations as well. The system may include an element similarity profile generator 630 configured to generate an element similarity profile 635. The system may contain a visual media classifier 665 configured to classify the unclassified visual media file as depicting or not depicting a vortex by using the element similarity profile and the third graphic property of the unclassified visual media file 680. In effect, the system uses the element similarity profile 635 and graphic property extracted from the unclassified visual media file to classify the visual media as depicting or not depicting a visual media file. In some cases, the visual media classifier 665 will assign a probability that an unclassified visual media file depicts or does not depict a visual media file.

FIG. 7 shows an exemplary method 700 according to aspect of the present application. FIG. 7 shows a method of detecting a travelling object travelling through air. FIG. 7 shows receiving an unclassified visual media file 705 from a first media collector at a first time; the first media collector having a field of view. A field of view is the region detectable or capturable by the media collector. A media collector may be configured to capture visual media files, the files are in a frame of the field of view of the media collector. The figure depicts generating an element similarity profile 710 by running the unclassified visual media file through a vortex similarity engine. The vortex similarity engine may be configured to determine 715 a vortex similarity ratio that the visual media file contains an image of a travelling object vortex. In some configurations, the method includes classifying the visual media file 720 as a travelling object vortex or not travelling object vortex. In some configurations, the method may include determining whether a travelling object is expected to be flying the field of view of the first media collector at the first time 725. Some configurations may include the steps of determining a travelling object's position as a function of time 730 (e.g. longitude, latitude, elevation), determining the media collector's field of view 735, determining an expected time for the media collectors to capture a visual media file of a vortex of the travelling object 740. The position of the travelling object may be determined via GPS, trip planning, LIDAR, communication with the travelling object, or other techniques.

The method shown in FIG. 7 optionally includes providing a flight plan 745. A flight plan may include one or more of the features from Table 1. In the configuration of FIG. 7 , the flight plan may be displayed with a flight recording and display 750. The flight plan optionally includes at least a validated flight field. The method may include setting the validated flight field to approved if a travelling object is expected to be flying at the first time in the field of view of the first media collector 755. The method may include setting the validated flight field to unapproved if a travelling object is not expected to be flying at the first time in the field of view of the first media collector 760. The method may include displaying the travelling object on a digital map if the travelling object is expected to be flying through the field of view of the first media collector at the first time 765. The method may include triggering an alert if no travelling object is expected be flying through the field of view of the first media collector at the first time 770.

FIG. 8 shows a schematic diagram of a system 800 for detecting a travelling object travelling through air. FIG. 8 depicts a vortex similarity engine 804 configured to receive an unclassified visual media file from a media collector 802. The vortex similarity engine may be configured to generate an element similarity profile 806 and/or a vortex similarity ratio 808. The system may comprise a visual media file classifier 810 configured to classify the unclassified visual media file as a travelling object vortex 812, not travelling object vortex 814, or unknown 816. A flight checker 826 may receive the classification data from the visual media file classifier 810. Position logic 818 may be configured to determine a position of the travelling object 820 and provide that position information to the flight checker 826. The position logic 818 may be configured to receive a transmission containing GPS information relating to a position of the travelling object. A travelling object position verification tool 824 may be configured to determine whether the travelling object is expected to be in the position determined by the travelling object position logic 818 or GPS receiver.

The flight checker 826 may comprise or be connected to a flight recorder 828 for saving or accessing a flight plan 830 comprising a plurality of rows of data. The flight plan 830 may comprise a flight ID 832 and validated flight field 834. The flight checker 826 may be configured to set the validated flight field 834 to: approved if a travelling object is expected to be flying at the first time in the field of view of the first media collector; and unapproved if a travelling object is not expected to be flying at the first time in the field of view of the first media collector.

The flight checker 826 may comprise or be connected to a flight visualizer 836 configured to display the travelling object on a digital map if the travelling object is expected to be flying through the field of view of the first media collector at the first time. The flight checker may comprise or be connected to an alert generator 838 configured to trigger an alert if no travelling object is expected be flying through the field of view of the first media collector at the first time.

FIG. 9 illustrates a method 900 of analyzing visual media file of travelling object vortices with a media file analyzer 910. The method may include generating graphic elements of the visual media files with a graphic recognition algorithm 920. The method may include identifying elements in common amongst the visual media files with an element profile generator to generate an element similarity profile 930. The method may include receiving an unclassified visual media file 940. The method may involve calculating a vortex similarity ration with a vortex similarity engine to indicate whether the visual media file depicts a vortex made by a travelling object vortex 950. The method may include classifying the visual media files as a travelling object vortex or not a travelling object vortex or unknown. Classification may be performed by a visual media file classifier 960. The system may trigger an alert with an alert generating if the visual media file classifier determines the receive unclassified visual media contains a travelling object vortex 970.

FIG. 10 shows a schematic diagram according to an aspect of the prevent invention. The system 1000 depicts a graphic recognition algorithm 1030 configured to analyze a first visual media file 1010A and a second visual media file 1010B. The media files may depict a travelling object vortex 1020 made by a travelling object 1015 or not a travelling object vortex. The system may include a vortex similarity engine 1025 comprising a graphic recognition algorithm 1030 configured to analyze the visual media files. An element generator 1035 may create graphic elements from the visual media file. The vortex similarity engine may comprise or be connected to a visual media file database 1005 optionally containing visual media file A, visual media B, and potentially more visual media files. The vortex similarity engine 1025 may include an element profile generator 1045 configured to identify an element in common amongst the visual media files and generate an element similarity profile 1040. The vortex similarity engine may be configured to receive an unclassified visual media file; compare the unclassified visual media file with the element similarity profile; and determine a travelling object vortex similarity ratio 1050 to indicate whether the visual media file depicts a travelling object vortex. The system may include a visual media classifier 1055 configured to classify the visual media files as a travelling object vortex or not travelling object vortex based on the travelling object cortex similarity ratio of the visual media file. The system may include an alert generator configured to generate an alert 1060 if the visual media file classifier determines the received unclassified visual media contains a travelling object vortex.

FIGS. 11-13 shows a flowchart of a method according to an aspect of the present invention. The method may include capturing a first, second, third, and N^(th) visual media of a subject (1110A-1110N). Subject meaning an object in the frame of the field of view of the media collector such as a travelling object, airborne object, travelling object, etc. The method may involve determining a vortex similarity ratio with the vortex similarity engine to indicate whether each of the visual media files contain a vortex by a travelling object (1120A-1120N). The method may include analyzing the visual media files with the vortex similarity engine to determine whether each of the visual media files depict a travelling object vortex (1130A-1130N). The method may include determining an overall travelling object vortex probability based on an aggregation of the three vortex similarity ratios using a probability calculator 1140. The method optionally includes triggering an alert if the overall craft vortex probability exceeds a predetermined threshold 1150.

The method 1100 may include verifying that the three visual media files depict the same subject using a media file identity verification tool. The method may include the step of triggering an alert if a majority of the visual media files analyzed by the vortex similarity engine have a vortex similarity ratio above a threshold value. The method may be configured wherein the first, second, and third media files are captured at different times, but still depict a single, same subject. The method may be configured wherein the first, second, and third media files are captured at different times, and all depict a travelling object vortex made by one travelling object.

Method 1200 may be configured wherein the first visual media file is captured at a first time 1210A; the second visual media file is captured at the first time 1210B; the third visual media is captured at the first time 1210C; and the first, second, and third media files are captured by different media collectors. The method may comprise determining a first, second, and third vortex similarity ratio (1220A-1220C) to determine whether the first, second, and third visual media depict a vortex (1230A-1230C). Although only three visual media files are shown in FIG. 12 , N number of images could be used some configurations. The method 1200 may include determining an overall travelling object vortex probability based on an aggregation of the three vortex similarity ratios using a probability calculator 1240. The method optionally includes triggering an alert if the overall travelling object vortex probability exceeds a predetermined threshold 1250.

Method 1300 may be configured wherein the first visual media file is captured by a first media collector; the second visual media file is captured by a second media collector; the third visual media file is captured by a third media collector; and the first, second, and third visual media files are captured at the same time (1310A-1310C). The method may comprise determining a first, second, and third vortex similarity ratio (1320A-1320C) to determine whether the first, second, and third visual media depict a vortex (1330A-1330C). Although only three visual media files are shown in FIG. 13 , N number of images could be used some configurations. The method 1300 may include determining an overall travelling object vortex probability based on an aggregation of the three vortex similarity ratios using a probability calculator 1340. The method optionally includes triggering an alert if the overall travelling object vortex probability exceeds a predetermined threshold 1350.

FIG. 14 illustrates a system 1400 comprising a visual media timing device 1405 configured to capture a first visual media file 1420A of a first subject; a second visual media file 1420B of a second subject; a third visual media file 1420C of a third subject; and a fourth visual media file 1420D of a fourth subject using a plurality of media collectors (1410A, 1410B, 1410C, 1410D). The system may comprise a vortex similarity engine 1425 configured to analyze the visual media files (1420A-1420D) with a visual media classifier 1440 to determine whether each of the visual media files depicts a travelling object vortex. The system 1400 may be configured to determine a vortex similarity ratio 1435 to indicate whether each of the visual media files depict a vortex made by a travelling object 1445. The system may comprise a probability calculator 1450 configured to determine an overall travelling object vortex probability based on an aggregation of the vortex similarity ratios. The system may comprise an alert trigger 1460 configured to trigger an alert if the overall travelling object vortex probability exceeds a predetermined threshold 1455.

The system may comprise a media file identity verification tool 1430 configured to verify whether the three visual media files depict the same subject. The system may comprise an alert trigger 1460 configured to trigger the alert if a majority of the visual media files analyzed by the vortex similarity engine have a vortex similarity ratio above a threshold value.

The visual media timing device 1405 may be configured to capture the visual media files at different times from different field of views. The visual media timing device may comprise: a first media collector configured to capture the first visual media file; a second media collector configured to capture the second visual media file; a N^(th) media collector configured to capture the N^(th) visual media; etc. and timing logic configured to capture the N media files at the same time. Although a one-to-one media collector: visual media file ratio is shown, other configurations are possible. The visual media timing device 1405 may comprise: a first media collector configured to capture the first visual media file; a second media collector configured to capture the second visual media file; an N^(th) media collector configured to capture the N^(th) visual media file; and timing logic to capture the N visual media files at different times.

FIG. 15 illustrates a flowchart depicting a method 1500 involving capturing a visual media file of a vortex made by a travelling object flying through a region of a media collector's field of view 1515. The travelling object may create a vortex in the region of air 1520. The method may comprise positioning a media collector to face a ground surface 1505 from an elevated position. The media collector may face a region of air above the ground surface. The media collector may capture one or more images or videos of the region above the ground surface 1510. The media collector may receive the images or videos with a computer 1530. The computer may detect whether the images or the videos resemble a vortex of a travelling object 1535; the vortex comprising a change in density of the air or compression of air molecules in the air 1525. The computer may determine whether the travelling object is on a registered flight plan 1540. The computer may trigger an alarm if the travelling object is not on a registered flight plan 1550. The computer may log the flight with a flight recorder into a flight plan as a validated flight if the travelling object is on a registered flight plan 1545.

FIG. 16 illustrates a schematic of system 1600. The system may comprise a media collector facing a ground surface from an elevated position 1605; wherein the media collector faces a region of air above the ground surface. The media collector may be configured to take a picture or a video of a vortex made by a travelling object flying through the field of view of the media collector. The media collector may be configured to capture one or more images or videos of the region above the ground surface 1610 when a travelling object flies through the region creating a vortex 1615. The system may comprise a computer configured to receive the images or video 1620. The computer may be configured to detect whether the images or the videos resemble a vortex of a travelling object 1625. A vortex may comprise a change in density of the air or compression of air molecules in the air. The computer may determine whether the travelling object is on a registered flight plan 1630. The system may comprise an alert generator configured to trigger an alarm if the travelling object is not on a registered flight plan 1635. The computer may comprise a flight recorder configured to log the flight into a flight manifest as a validated flight if the travelling object is on a registered flight plan 1640.

A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the disclosure. For example, various forms of the flows shown above may be used, with steps re-ordered, added, or removed. Accordingly, other implementations are within the scope of the following claims.

For instances in which the systems and/or methods discussed here may collect personal information about users, or may make use of personal information, the users may be provided with an opportunity to control whether programs or features collect personal information, e.g., information about a user's social network, social actions or activities, profession, preferences, or current location, or to control whether and/or how the system and/or methods can perform operations more relevant to the user. In addition, certain data may be anonymized in one or more ways before it is stored or used, so that personally identifiable information is removed. For example, a user's identity may be anonymized so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained, such as to a city, ZIP code, or state level, so that a particular location of a user cannot be determined. Thus, the user may have control over how information is collected about him or her and used.

Embodiments may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more of them. The term “data processing system” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The system may include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus.

Embodiments and functional operations described in this specification may be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. For example, elements designated as engines, generators, identifiers, tools, analyzers, calculators, classifiers, checkers, finders, logic recorders, visualizers, aggregators, modules, nodes, managers, organizers, algorithms, etc. may be implemented in a variety of ways. A computer program (also known as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code).

A computer program may be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification may be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be performed by, and apparatus may also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both.

The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer may be embedded in another device, e.g., a tablet computer, a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name just a few. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.

To provide interaction with a user, embodiments may be implemented on a computer having a display device, like a TV or monitor (CRT or LCD, etc.) for displaying information to the user. Computers may have peripherals like a keyboard, trackpad, mouse, etc. Other kinds of devices may be used to provide for interaction with a user as well; for example, feedback provided to the user may be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including acoustic, speech, or tactile input.

Embodiments may be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a web browser through which a user may interact with an implementation, or any combination of one or more such back end, middleware, or front end components. The components of the system may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.

The computer and/or computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

While this specification contains many specifics, these should not be construed as limitations on the scope of the disclosure or of what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features that are described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.

In each instance where an HTML file is mentioned, other file types or formats may be substituted. For instance, an HTML file may be replaced by an XML, JSON, plain text, or other types of files. Moreover, where a table or hash table is mentioned, other data structures (such as spreadsheets, relational databases, or structured files) may be used.

Thus, particular embodiments have been described. Other embodiments are within the scope of the following claims. For example, the actions recited in the claims may be performed in a different order and still achieve desirable results. 

What is claimed is:
 1. A system for determining whether an unclassified visual media file depicts a vortex comprising: a visual media file database comprising a first visual media file and second visual media file; a first graphics recognition algorithm configured to determine: a first graphic property of the first visual media file; a second graphic property of the second visual media file; a third graphic property of the unclassified visual media file; a graphic property manager configured to save the first graphic property and second graphic property; an element profile generator configured to generate an element similarity profile; the element similarity profile comprising elements; a visual media classifier configured to: classify the unclassified visual media file as depicting or not depicting a vortex by using the element similarity profile and the third graphic property of the visual media file; and generate a similarity value based on how similar the elements in the visual media file are to previously captured and identified travelling object vortices.
 2. The system of claim 1 wherein the system is configured to detect whether the vortex was generated by a UAS (unmanned aircraft system) or a UAV (unmanned aircraft vehicle).
 3. The system of claim 1 wherein the system is configured to detect whether the vortex was made by a fixed wing airplane.
 4. The system of claim 1 wherein the system is configured to detect whether the vortex was made by a missile or a projectile.
 5. The system of claim 1 wherein the system is configured to detect whether the vortex was made by a drone.
 6. The system of claim 1 wherein the system is configured to detect whether the vortex was made by a ship.
 7. The system of claim 1 wherein the system is configured to detect whether the vortex was made by a submarine.
 8. A system comprising: a database comprising a visual media file; a computer configured to: detect whether the visual media file resembles a vortex of a travelling object; generate a similarity value based on how many elements the visual media file has with previously captured and identified visual media files of travelling object vortices; and flight plan logic configured to: determine whether the travelling object is on a registered flight plan; and trigger an alarm when the travelling object is not on a registered flight.
 9. The system of claim 8 wherein the computer is programmed to detect whether the visual media file has elements in common with a vortex generated by a travelling object.
 10. The system of claim 8 wherein the computer is configured to generate a similarity value based on how many elements the visual media file has in common with previously captured and identified visual media files of travelling object vortices.
 11. The system of claim 8 wherein in the computer is configured to generate a similarity value based on how similar the elements in the visual media file are to previously captured and identified visual media files of travelling object vortices.
 12. The system of claim 8 wherein the computer is configured to designate the visual media file as a travelling object vortex visual media file when the visual media file depicts a travelling object vortex.
 13. The system of claim 8 wherein the computer is configured to designate the visual media file as not a travelling object vortex visual media file when the visual media file does not contain a travelling object vortex.
 14. The system of claim 13 wherein the computer is configured to: identify a graphic property that some of the travelling object vortex visual media files share with a graphic recognition algorithm; and generate an element similarity profile based on one or more graphic elements identified by the graphic recognition algorithm.
 15. The system of claim 14 wherein the computer is configured to generate graphic elements based on characteristics of images in the database.
 16. The system of claim 8 wherein the system is configured to detect whether the vortex was generated by a UAS (unmanned aircraft system) or a UAV (unmanned aircraft vehicle).
 17. The system of claim 8 wherein the system is configured to detect whether the vortex was made by a fixed wing airplane.
 18. The system of claim 8 wherein the system is configured to detect whether the vortex was made by a missile or a projectile.
 19. The system of claim 8 wherein the system is configured to detect whether the vortex was made by a drone.
 20. The system of claim 8 wherein the system is configured to detect whether the vortex was made by a ship.
 21. The system of claim 8 wherein the system is configured to detect whether the vortex was made by a submarine.
 22. A method comprising: storing a visual media file in a database; detecting whether the visual media file resembles a vortex of a travelling object; generating a similarity value based on how many elements the visual media file has in common with previously captured and identified visual media files of travelling object vortices; determining whether the travelling object is on a registered flight plan; and triggering an alarm when the travelling object is not on a registered flight.
 23. The method of claim 22 comprising detecting whether the visual media file has elements in common with a vortex generated by a travelling object.
 24. The method of claim 22 comprising generating a similarity value based on how many elements the visual media file has in common with previously captured and identified visual media files of travelling object vortices.
 25. The method of claim 22 comprising generating a similarity value based on how similar the elements in the visual media file are to previously captured and identified visual media files of travelling object vortices.
 26. The method of claim 22 comprising designating the visual media file as a travelling object vortex visual media file when the visual media file depicts a travelling object vortex.
 27. The method of claim 22 comprising: identifying a graphic property that some of the travelling object vortex visual media file share with a graphic recognition algorithm; and generating an element similarity profile based on one or more graphic elements identified by the graphic recognition algorithm.
 28. The method of claim 22 comprising detecting whether the vortex was made by a drone.
 29. The method of claim 22 comprising detecting whether the vortex was made by a fixed wing aircraft. 